home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
stdump.z
/
stdump
Wrap
Text File
|
1998-10-30
|
5KB
|
133 lines
SSSSTTTTDDDDUUUUMMMMPPPP((((1111)))) SSSSTTTTDDDDUUUUMMMMPPPP((((1111))))
NNNNAAAAMMMMEEEE
stdump - dump a file of intermediate-code debugging information
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ssssttttdddduuuummmmpppp [-a] [-b] [-c] [-g] [-h] [-i] [-n number] _f_i_l_e
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
When compiling for the old 32-bit ABI (-32), the compilers generate an
intermediate language which is separated into binary instructions and
debugging information, each constituting a separate file. Use _s_t_d_u_m_p to
dump a file containing debugging information which was generated by the
compilers. _s_t_d_u_m_p writes to the standard output. The organization of the
output is simple but the details of the output are complicated. The
detailed output is be defined here. The output of _s_t_d_u_m_p is subject to
change and one should not rely on the output format remaining the same
from release to release.
The organization of the output is: for each source file represented in
_f_i_l_e there may be auxiliary-symbols, local-symbols, a file-indirect-
table, optimization-entries, procedures, and line-numbers; there is only
one externals-table and one dense-number-table in _f_i_l_e.
By default, _s_t_d_u_m_p prints all information about all sections of the
debugging information. The options (described below) restrict the output
to the selected sections.
The _f_i_l_e may be an object file (such as produced by cc -c) or an
executable file (such as produced by _l_d(_1) or _c_c(1)) or a debugging
information file (which may be produced as described below).
Normally, debugging information files (and instruction files) are placed
in /tmp and removed after each compilation. Use the ----kkkkeeeeeeeepppp option to _c_c,
or _f_7_7(1) to force the compiler to preserve these files in the target
directory. When this switch is used, the compilation of ffffiiiilllleeee...._x (where _x
is c for C or f for FORTRAN, for example) will produce the intermediate
files ffffiiiilllleeee...._B (instructions) and ffffiiiilllleeee...._T (debugging information). The
latter file (ffffiiiilllleeee...._T) may be used as input to _s_t_d_u_m_p.
The following options are recognized:
----aaaa Print the dense number table. This section is empty for object
and executable files.
----bbbb Print the externals table.
----cccc Print the local debugging symbols. The source file name is
printed here.
----gggg Print the auxiliaries table. This table has encoded in it in a
complex way the actual data types of all the data in the symbols.
The local-symbol and externals table sections show this data
expanded into semi-readable text.
PPPPaaaaggggeeee 1111
SSSSTTTTDDDDUUUUMMMMPPPP((((1111)))) SSSSTTTTDDDDUUUUMMMMPPPP((((1111))))
----hhhh Print the line table. One source line number per 32-bits of
executable code.
----iiii Print the File Indirect Table.
----nnnn nnnnuuuummmmbbbbeeeerrrr
Print information about only the source file whose number is
given. Files are numbered sequentially starting with zero.
FFFFIIIILLLLEEEESSSS
/tmp/ctmsta_x_x_x_x_x default name of debugging information file for process
id _x_x_x_x_x
_f_i_l_e.T name of debugging information file created by the ----kkkkeeeeeeeepppp
option
/usr/bin/stdump debugging information dump program
SSSSEEEEEEEE AAAALLLLSSSSOOOO
elfdump(1), dwarfdump(1), cc(1), f77(1), pc(1), abi(5)
NNNNOOOOTTTTEEEESSSS
One cannot use stdump to display the debugging information of 64-bit (-
64) or new 32bit ABI (-n32) object files. Use dwarfdump(1) instead.
To see the linking information, use _e_l_f_d_u_m_p(1) instead of _s_t_d_u_m_p.
PPPPaaaaggggeeee 2222